Stop requiring a licence token managed Intelligence no longer issues - #362
Merged
Conversation
Managed Intelligence derives entitlement from the project key, so there is no second credential to fetch. This repository was the loudest remaining source of the two-key story: runtimeCapabilities() refused to boot without COPILOTKIT_LICENSE_TOKEN, and prompt.txt, .env.example, the README, three docs and the chart all taught people to go and find one. The token is now optional everywhere and still forwarded when set, which is what a self-hosted Intelligence with its own licence needs. The chart failed harder than the docs did: secret.yaml and validation.yaml both required secrets.licenseToken, so a managed-Intelligence install was blocked outright rather than merely misdocumented. Also bumps @copilotkit/runtime and react-core to 1.70.1, which moved @ag-ui/* to 0.0.59; leaving the old 0.0.57 pins split AbstractAgent into two incompatible declarations and broke typecheck.
davidmckayv
requested review from
MikeRyanDev,
guidovizoso and
tylerslaton
as code owners
September 4, 2026 16:13
mxmzb
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Managed Intelligence derives entitlement from the project key and issues no licence token, so asking for a second credential sent people hunting for something that no longer exists. This repository was the loudest remaining source of that story.
What changed
runtimeCapabilities()required all four Intelligence values. Now three:INTELLIGENCE_API_URL,INTELLIGENCE_GATEWAY_WS_URL,INTELLIGENCE_API_KEY.COPILOTKIT_LICENSE_TOKENis optional and still forwarded to the runtime when set, which a self-hosted Intelligence with its own licence needs.@copilotkit/runtimeitself declareslicenseTokenoptional.The chart failed harder than the docs.
secret.yamlandvalidation.yamlboth requiredsecrets.licenseToken, so a managed-Intelligence install was blocked athelm installrather than merely misdocumented.Then every surface that taught the two-key setup:
prompt.txt,.env.example,README.md,docs/{configuration,development,deployment}.md,charts/openbot/README.md, and thestart.shfailure hint that told people to runlicense --write.Dropped the fake licence from the CI smoke, so CI now proves boot without one.
Dependency bump
@copilotkit/runtimeand@copilotkit/react-core1.69.0 → 1.70.1, which moved@ag-ui/*to 0.0.59. The old 0.0.57 pins inserver/package.jsonandapp/package.jsonleft two copies of@ag-ui/clientand splitAbstractAgentinto incompatible declarations, breaking typecheck.Verification
check-rendered-chart.tsboth with and without a licence: zero licence references when unset, three when setCOPILOTKIT_LICENSE_TOKENabsent from the env file:/health200,/api/copilotkit/info200,licenseStatusstillvalid, all three Bots registered, so thestart.shgate passes